Compare jcommonsense qa prompts with question first vs last #113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kumapo
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As reported by this article, jcommonsense qa prompts that puts question last results in better performance.
And, as you see the results in following table, I reproduced the performance jump with the prompts by changing only the order of question.
But currently, 0.3 and 0.6 prompts put the question last, and the others put it first.
To ensure a fair model comparison, prompts should have the question in the same position.
What do you think if we add prompts that put the question last or update the current prompts to have the question last?
If I missed something to experiment, please let me know.